OpenEdge Getting Started:<br />Progress OpenEdge Studio OpenEdge Studio tools

The descriptions of the OpenEdge tools are listed in the order in which they appear in the Tools menu. An asterisk (*) indicates that you can also access the tool from a tool icon. If a tool has not been licensed or installed at your site, its icon does not appear in the Desktop.

Data dictionary* — A tool used to define the structure of your database including tables, fields, and indexes, and to generate reports about the database. You can use this tool to define application defaults that, for example, validate data, perform security checks, and generate unique sequence numbers. The Progress 4GL gives you the flexibility to override most of these defaults in individual applications.

You can also use the Data Dictionary to create and connect to databases.

Procedure editor* — An editor used to create, edit, compile, and run unstructured 4GL procedures (as opposed to the structured procedures created by the AppBuilder). The Procedure Editor also provides functionality for checking syntax, managing multiple files, and customizing its environment.

Data administration — A tool used to perform a variety of database administration tasks including creating, starting, and shutting down databases, dumping and loading database files, importing and exporting data, and implementing database security.

PRO*Tools — A set of utility programs to aid in developing and running applications in the OpenEdge Studio. For example, one of the PRO*Tools allows you to edit your PROPATH, the path OpenEdge searches to find programs. When you select PRO*Tools from the Tools menu, the OpenEdge Studio displays a resizable palette of icons. You then run an individual PRO*Tool by clicking on its icon.

AppBuilder* — The basic visual programming tool in the OpenEdge Studio. You fabricate and assemble application components in the AppBuilder. The Section Editor aids in editing 4GL code convientently while preserving the standardized structure that works best with OpenEdge application components, such as basic objects and SmartObjects.

Web tools — Tools used to monitor your Web server environment, manipulate objects such as deleting and checking syntax, viewing database schema information, and issuing operating system commands through an intuitive browser interface that also provides links to sample applications and support services.

Results* — An interactive menu-driven tool that lets end users with little or no programming experience query, report on, and maintain information stored in database tables. As an application developer, you can also customize Results according to the needs of individual sites, and then integrate it into your applications.

Translation Manager* — A tool used to manage the process of customizing an application for specific end-user languages. Translation Manager allows you to select words and phrases from source procedure files for translation into other languages. These words and phrases are assembled into translation kits that you can send to translators who perform the actual translation. After you receive the completed translations, you use the Translation Manager to review the translations and integrate them into your applications. The Translation Manager also provides statistical information about your translation projects.

Visual Translator — A tool used by the translators who translate the actual words and phrases into other languages. The Visual Translator uses a translation kit that was generated by the Translation Manager, and allows the translator to work either from a list or in the visual context of an application’s windows.

Application compiler — A tool used to compile individual source procedures or a group of procedures to produce executable code that is permanently stored.

Application debugger* — An interactive tool used to monitor the execution of an application by stopping and restarting it at specified lines. You can also display or update information about the procedure you are running (such as the names and values of variables) without modifying any procedure code. The Debugger runs as a separate process with its own window.